docs(roadmap): add upstream A2A interoperability workstream - #113
Merged
Conversation
Our conformance suite says a peer implements cA2A. It says nothing about whether attaching the profile keeps us compatible with the wider A2A ecosystem. Records the plan to answer that with numbers: a2a-tck first, then the A2A Interoperability Test Kit multi-language launcher. Also records two things that are easy to get wrong. The system under test is an a2a-sdk server with the extension attached, not `ca2a start`, since a normative A2A transport is out of scope for the profile. And the protobuf Struct integer-ness round trip is only tested safe in Python.
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records a workstream that was agreed but written down nowhere: running cA2A against the upstream A2A conformance and interoperability harnesses, and publishing the result with the gaps included.
Our own
tests/conformance/suite answers "does this peer implement cA2A". It does not answer "does attaching the profile keep us compatible with the rest of the A2A ecosystem", which is a separate question and a more interesting one to have numbers for.Two things in here are guardrails rather than plan, because both are easy to get wrong:
a2a-sdkserver with the extension attached throughca2a_runtime.transport.a2a_sdk, notca2a start.LIMITATIONS.mdputs a normative A2A transport out of scope, so a conformance suite aimed at the reference standard-library transport would fail baseline MUSTs for reasons that say nothing about the profile.Structinteger-ness round trip already documented intransport/a2a_sdk.pyis tested safe in Python only. Go and Rust are assumptions, and the ITK launcher now covers both.Docs only, no code paths touched.